Skip to content

fix: hydrate authenticated user in Studio#3043

Open
edschema wants to merge 1 commit intoopenedx:masterfrom
Schema-Education:schema/avatar-fix
Open

fix: hydrate authenticated user in Studio#3043
edschema wants to merge 1 commit intoopenedx:masterfrom
Schema-Education:schema/avatar-fix

Conversation

@edschema
Copy link
Copy Markdown

@edschema edschema commented Apr 30, 2026

Description

Studio needs hydrated authenticated-user account data so the header can receive uploaded Open edX profile image metadata.

The initial JWT-derived authenticatedUser object contains sparse identity data, but uploaded profile image URLs are exposed by the account API under authenticatedUser.profileImage after authenticated-user hydration. This change enables that existing frontend-platform hydration path for Studio by adding:

hydrateAuthenticatedUser: true

to the app initialization options.

Dependency / Staging Note

Draft until the header package change is released.

This PR depends on:

That PR teaches StudioHeader to use hydrated authenticatedUser.profileImage data while preserving the legacy authenticatedUser.avatar contract.

Before this PR is ready to merge, frontend-app-authoring should update @edx/frontend-component-header and package-lock.json to the released package version that includes the header normalization. Without that package update, this PR enables hydration but the app still consumes the currently locked header package, so the uploaded avatar will not render yet.

Testing

npm run types

Related package verification from frontend-component-header:

npm test -- --runTestsByPath src/studio-header/StudioHeader.test.tsx --runInBand
npm run types

@openedx-webhooks openedx-webhooks added the open-source-contribution PR author is not from Axim or 2U label Apr 30, 2026
@openedx-webhooks
Copy link
Copy Markdown

openedx-webhooks commented Apr 30, 2026 •
edited
Loading

Thanks for the pull request, @edschema!

This repository is currently maintained by @bradenmacdonald.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details
Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

@github-project-automation github-project-automation Bot moved this to Needs Triage in Contributions Apr 30, 2026
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 30, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.52%. Comparing base (da4e81b) to head (10e8edc).

Additional details and impacted files 
@@           Coverage Diff            @@
##           master    #3043    +/-   ##
========================================
  Coverage   95.52%   95.52%            
========================================
  Files        1392     1392            
  Lines       32911    32911            
  Branches     7340     7574   +234     
========================================
  Hits        31437    31437            
  Misses       1419     1419            
  Partials       55       55

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@bradenmacdonald
Copy link
Copy Markdown
Contributor

bradenmacdonald commented Apr 30, 2026

Fixes #3041

@edschema edschema marked this pull request as ready for review April 30, 2026 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

open-source-contribution PR author is not from Axim or 2U

Projects

Contributions
Status: Needs Triage

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@edschema @openedx-webhooks @bradenmacdonald